fix(install): resolve GPG key verification failures on RHEL platforms #810
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add execute resource to import GPG key into RPM database - Set repo_gpgcheck=false to work around metadata signature issues - Add KITCHEN_LOCAL_YAML to mise.toml for Dokken driver - Enhance TESTING.md with comprehensive local development guide - Create FAILING_TESTS.md to track test failures and fixes Root cause: DNF on RHEL 9+ requires GPG keys to be imported into the RPM database, not just present as files. Additionally, repo metadata signatures can cause issues even when package signatures are valid. This fix enables all RHEL-based platform testing which were previously blocked. Signed-off-by: Dan Webb <[email protected]>
PostgreSQL uses different GPG keys for signing aarch64 vs x86_64 packages. The previous fix attempted to import the generic key, but packages were still failing verification because they were signed with arch-specific keys. Changes: - Update default_yum_gpg_key_uri helper to detect architecture - Use PGDG-RPM-GPG-KEY-AARCH64-RHEL for aarch64 on RHEL 8+ - Use PGDG-RPM-GPG-KEY-AARCH64-RHEL7 for aarch64 on RHEL 7 - Keep generic keys for x86_64 architecture - Remove not_if guard from rpm import (command is idempotent) Verified on: - centos-stream-9 (aarch64): PASSING - rockylinux-9 (aarch64): PASSING - debian-12 (aarch64): PASSING This fully resolves the GPG verification failures on RHEL-based platforms.
Use >= 7.2 instead of >= 7.2.0 per Chef metadata best practices. Version constraints should use major.minor format without patch version.
Signed-off-by: Dan Webb <[email protected]>
damacus
force-pushed
the
fix-up
branch
4 times, most recently
from
4acbe37 to
faa200e
Compare
Signed-off-by: Dan Webb <[email protected]>
Slowest examplesTop 10 slowest examples (0.01 seconds, 48.72% of total time)
|
Slowest examplesTop 10 slowest examples (0.01 seconds, 48.28% of total time)
|
bmhughes
approved these changes
Oct 21, 2025
bmhughes
added
Bug
Copilot AI
pushed a commit
that referenced
this pull request
Oct 21, 2025
…#810) * fix(install): resolve GPG key verification failures on RHEL platforms - Add execute resource to import GPG key into RPM database - Set repo_gpgcheck=false to work around metadata signature issues - Add KITCHEN_LOCAL_YAML to mise.toml for Dokken driver - Enhance TESTING.md with comprehensive local development guide - Create FAILING_TESTS.md to track test failures and fixes Root cause: DNF on RHEL 9+ requires GPG keys to be imported into the RPM database, not just present as files. Additionally, repo metadata signatures can cause issues even when package signatures are valid. This fix enables all RHEL-based platform testing which were previously blocked. Signed-off-by: Dan Webb <[email protected]> * fix(install): use architecture-specific GPG keys for RHEL platforms PostgreSQL uses different GPG keys for signing aarch64 vs x86_64 packages. The previous fix attempted to import the generic key, but packages were still failing verification because they were signed with arch-specific keys. Changes: - Update default_yum_gpg_key_uri helper to detect architecture - Use PGDG-RPM-GPG-KEY-AARCH64-RHEL for aarch64 on RHEL 8+ - Use PGDG-RPM-GPG-KEY-AARCH64-RHEL7 for aarch64 on RHEL 7 - Keep generic keys for x86_64 architecture - Remove not_if guard from rpm import (command is idempotent) Verified on: - centos-stream-9 (aarch64): PASSING - rockylinux-9 (aarch64): PASSING - debian-12 (aarch64): PASSING This fully resolves the GPG verification failures on RHEL-based platforms. * chore: fix yum dependency version constraint Use >= 7.2 instead of >= 7.2.0 per Chef metadata best practices. Version constraints should use major.minor format without patch version. * chore: add gpg cookbook dependency Signed-off-by: Dan Webb <[email protected]> * Remove CentOS 8 based platforms from testing Signed-off-by: Dan Webb <[email protected]> --------- Signed-off-by: Dan Webb <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Root cause: DNF on RHEL 9+ requires GPG keys to be imported into the RPM database, not just present as files. Additionally, repo metadata signatures can cause issues even when package signatures are valid.
This fix enables all RHEL-based platform testing which were previously blocked.